docs: fix navigation.json path in adding-pages guide and typos in blog posts - #9158
Open
toyeshhm wants to merge 1 commit into
Open
docs: fix navigation.json path in adding-pages guide and typos in blog posts#9158toyeshhm wants to merge 1 commit into
toyeshhm wants to merge 1 commit into
Conversation
…g posts docs/adding-pages.md tells contributors twice to edit `app/site/navigation.json`, which does not exist. The file is `apps/site/navigation.json`. Also fix misspellings in the English blog posts: occuring, effected, additon, millenia, rewritting, overwitten, encounted, retrive, interuption, priviledges, serverity, delievered, protoype, annoucement. Signed-off-by: toyeshhm <toyeshhm@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
docs/adding-pages.mdtells contributors twice (lines 76 and 95) to register new pages inapp/site/navigation.json. That path does not exist; the file isapps/site/navigation.json. Anyone following the "Adding Learn Pages" guide is sent to a nonexistent file.Also fixes misspellings in the English blog posts:
blog/announcements/making-nodejs-downloads-reliable.md: occuring → occurring, "being effected" → "being affected", additon → additionblog/community/2025-pride.md: millenia → millenniablog/events/collab-summit-2025-paris.md: rewritting → rewritingblog/vulnerability/february-2024-security-releases.md: overwitten → overwritten, encounted → encounteredblog/vulnerability/august-2023-security-releases.md: retrive → retrieve (heading)blog/vulnerability/june-2023-security-releases.md: interuption → interruption (heading)blog/vulnerability/february-2023-security-releases.md: priviledges → privilegesblog/vulnerability/july-2022-security-releases.md: serverity → severityblog/vulnerability/openssl-fixes-in-regular-releases-may2022.md: serverity → severity, delievered → deliveredblog/vulnerability/jan-2022-security-releases.md: protoype → prototypeblog/vulnerability/aug-2021-security-releases2.md: annoucement → announcementTwo of the fixes are in headings of security release posts, so their generated anchor ids change. Happy to drop those two if any inbound links depend on the old anchors.
Validation
Markdown-only changes; no code touched. Reviewed each line in context. Did not run the pnpm format/test/build steps locally since only
.mdfiles are edited; CI will confirm.Related Issues
None.
Check List
pnpm formatto ensure the code follows the style guide.pnpm testto check if all tests are passing.pnpm buildto check if the website builds without errors.